Repository navigation
Conversation
Text fields only focused visually by the toolkit, but not by X11 underneath semantically, so the host can still consume Space and other shortcuts instead of letting them reach the field. Practically speaking, this means that if you type a space in the text field of A/B, it triggers start/stop in REAPER. Fix this by letting widgets say whether they need native focus, and update it when the focused widget changes. This depends on lsp-plugins/lsp-ws-lib#8
|
Hello! |
|
You broke it in your devel branch. It needs to relinquish focus when selecting a non-textedit control. In my code, it does this. In your new commit, it does not. Focus is only then relinquished when selecting REAPER again, but not when selecting a non-textedit control within the plugin. |
|
@zx2c4 It appears that this commit fixes it: 9d7d593 But now we have troubles with REAPER:
The reason is that LSP window does not receive any FocusOut event in this scenario. |
|
If you revert all your commits and use my original, does that still happen? |
Text fields only focused visually by the toolkit, but not by X11 underneath semantically, so the host can still consume Space and other shortcuts instead of letting them reach the field. Practically speaking, this means that if you type a space in the text field of A/B, it triggers start/stop in REAPER. Fix this by letting widgets say whether they need native focus, and update it when the focused widget changes.
This depends on lsp-plugins/lsp-ws-lib#8